home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Aminet 40
/
Aminet 40 (2000)(Schatztruhe)[!][Dec 2000].iso
/
Aminet
/
misc
/
emu
/
msh-156.lha
/
mountshare
/
mountshare.man
< prev
next >
Wrap
Text File
|
1992-02-16
|
6KB
|
199 lines
MountShare(1l) Amiga Programmer's Manual MountShare(1l)
1mUSAGE
0musage: MountShare {{[+-][lchdf]} {<devicename>}}
+l: load Handler/FileSystem file
+c: create FileSysEntry
-h: don't compare Handler/FileSystem filenames
-d: don't compare DosType values
+f: search FileSysEntries
The option opposite to default is shown.
The use of MountShare is as follows. Suppose you have some
filesystem or other handler that you wish to mount multiple
times. For example, you might have the following in your
mountlist:
PIP: Handler = L:ConHandler
StackSize = 600
Priority = 5
GlobVec = 0
#
CNC: Handler = L:ConHandler
StackSize = 600
Priority = 5
GlobVec = 0
#
If you mount and use both of PIP: and CNC:, the result will
be that the handler L:ConHandler is loaded twice. This is
clearly a waste of memory, since many handlers are PURE
code.
4mNote0m: 4mMountShare0m 4mshould0m 4mONLY0m 4mbe0m 4mused0m 4mwith0m 4mrespect0m 4mto0m 4mPURE0m
4mhandlers0m. Examples of pure handlers are: L:ConHandler
(ConMan), L:FastFileSystem, newer versions of
MessyFileSystem (1.51 and higher), L:Port-Handler (PRT:,
SER: and PAR:).
MountShare will allow you to re-use the loaded code from one
device for other devices that are applicable. Using
MountShare you specify a "master" device whose handler will
be re-used by other devices. (The word "device" in this
document is used for an AmigaDOS device, not for an Exec
.device.)
This is done in the following way:
- Optionally, the master handler is loaded if necessary.
Otherwise sharing it would not have any effect.
- Optionally, the handler is made available on the
FileSystem.resource list. This can only be done if the
master has a proper DosType value.
- If the other device specifies the same filename for the
handler, the master code is shared. Otherwise,
- if the other device has the same DosType value specified
in the Mountlist information, the master code is shared.
Rhialto, KosmoSoft -1-
MountShare(1l) Amiga Programmer's Manual MountShare(1l)
Otherwise,
- optionally, if the other device has a DosType for which a
FileSystem.resource handler is available, that code is
shared.
Another application of MountShare is when you have a
harddisk with the FastFileSystem, and later you want to
mount more partitions (or floppies) using the FFS. Since all
FFS devices are identified by the line
DosType = 0x444F5301
you can mount all these devices, then use MountShare to
share the FFS code between all of them. If your harddisk
does not automount you may want to specify the +l option.
1mEXAMPLES
0mThe second example assumes you installed ConMan. ConMan
changes the CON: device as if it had the same mountlist as
given for PIP: and CNC: above.
1> MountShare +l ser
L:PORT-HANDLER loaded.
SER and PRT share handler L:PORT-HANDLER: SegList copied.
SER and PAR share handler L:PORT-HANDLER: SegList copied.
1> Mount PIP: CNC:
1> MountShare CON
CON and CNC share handler L:ConHandler: SegList copied.
CON and PIP share handler L:ConHandler: SegList copied.
1mCAVEATS
0m4mMountShare0m 4mshould0m 4mONLY0m 4mbe0m 4mused0m 4mwith0m 4mrespect0m 4mto0m 4mPURE0m
4mhandlers0m.
Of course, you should use MountShare before using the
device, because otherwise the handler will be loaded by
AmigaDOS and there won't be much to share.
Similarly, you should not have the line
Mount = 1
in your mountlist entry, since the Mount command will load
the handler unconditionally in this case.
If you decide to share a file system handler, or add it to
the FileSystem.resource, the handler should never be
unloaded again. If the handler has the ability to unload
itself, this should not be used.
1mFUTURE COMPATIBILITY
0mEverything that MountShare does should be done by a smart
Mount command. Perhaps this will be implemented by
Commodore in a future version.
Rhialto, KosmoSoft -2-
MountShare(1l) Amiga Programmer's Manual MountShare(1l)
1mBUGS
0mOther processes should not change the device list or
FileSystem.resource list while we are running.
1mAUTHOR
0mCopyright 1992 by Olaf 3mRhialto 0mSeibert. All rights
reserved.
Rhialto, KosmoSoft -3-